翻訳と辞書 Words near each other ・ Logie Award for Best News Panel or a Current Affairs Program ・ Logie Award for Best Presenter ・ Logie Award for Best Reality Program ・ Logibec Groupe Informatique ・ Logic ・ Logic (disambiguation) ・ LOGIC (electronic cigarette) ・ Logic (rapper) ・ Logic (song) ・ Logic alphabet ・ Logic analyzer ・ Logic as a Positive Science ・ Logic block ・ Logic bomb ・ Logic built-in self-test ・ Logic centralization pattern ・ Logic Control ・ Logic error ・ Logic Express ・ Logic family ・ Logic File System ・ Logic for Computable Functions ・ Logic for Programming, Artificial Intelligence and Reasoning ・ Logic form ・ Logic game ・ Logic gate ・ Logic Group of Schools ・ Logic in China ・ Logic in computer science ・ Logic in Islamic philosophy Dictionary Lists mini英和辞書 mini和英辞書 Webster 1913 Latin-English FOLDOC Wikipedia English ウィキペディア

翻訳と辞書　辞書検索 [ 開発暫定版 ] スポンサード リンク Logic centralization pattern ： ウィキペディア英語版 Logic centralization pattern Logic Centralization is a design pattern, applied within the service-orientation design paradigm, whose application aims to increase the reusability potential of agnostic logic 〔Logic that does not belong to a specific business process and hence can be reused to automate multiple business processes〕 by ensuring that services〔(Services )〕 do not contain redundant agnostic logic and that any reusable logic should only be represented by a service that has the most suitable functional context.〔The type of the functionality provided by the service.〕〔Kanu Tripathi.(Service Transaction Handling Without WS-AtomicTransaction )().Date accessed: 25 April 2010.〕 ==Rationale== As more and more services are developed, there is a constant risk that services with redundant functionality may be created. Although the application of the Service Normalization design pattern does help to eliminate this redundancy, however, just by having a set of normalized services on its own, does not guarantee that they would be reused as originally envisaged. In case of agnostic services,〔Services that contain agnostic logic〕 this issue can severely restrict the actual reuse of such services because a project team (Team A) may decide no to reuse an existing service, e.g. it requires data that corresponds to a complex schema, and instead develop a lightweight service that just does the job. As a result, the same reusable logic now exists with two different services, whereas the existing service should have been evolved even if it did not contain the most suitable flavor of the functionality. This effect gets multiplied when another team (Team B) hoping to find the functionality within the existing service, as the boundary of the service does cover the required functionality, fails to find it and instead start using the newly created service by Team A. Consequently, the actual reusability of the original agnostic service drops and at the same time creates governance problem as far as the maintenance of the original and new services is concerned because now reusable logic exists in a decentralized manner. In order to ensure that a particular type of reusable solution logic is only enclosed by one specific agnostic service, the Logic Centralization design pattern dictates that design standards need to be established that force the proper use of agnostic services. This gives the service consumers the confidence that they are accessing the functionality through the correct service.〔Dennis Wisnosky.(Principles and Patterns at the U.S. Department of Defense )().Date accessed: 25 April 2010.〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Logic centralization pattern」の詳細全文を読む スポンサード リンク 翻訳と辞書 : 翻訳のためのインターネットリソース Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.